The IDPS must capture and log sufficient information to establish the identity of any user accounts associated with the sensor log event.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-34600	SRG-NET-999999-IDPS-00218	SV-45466r1_rule		Low

Description
Log records content that may be necessary to satisfy the requirement of this control includes: timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. This capability is critical for accurate forensic analysis.

STIG	Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide	2012-11-19

Details

Check Text ( C-42815r1_chk )
Examine the IDPS central sensor log. Search for events showing some or all of the following is being logged, as applicable, to the exiting entries: timestamps, source and destination addresses, user or process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. If sufficient information to establish the identity of any user accounts associated with the event is not captured and logged, this is a finding.

Check Text ( C-42815r1_chk )

Examine the IDPS central sensor log.
Search for events showing some or all of the following is being logged, as applicable, to the exiting entries: timestamps, source and destination addresses, user or process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.

If sufficient information to establish the identity of any user accounts associated with the event is not captured and logged, this is a finding.

Fix Text (F-38863r1_fix)
Configure the IDPS to capture and log the following at a minimum: timestamps, source and destination addresses, user or process identifiers, event descriptions, success or failure indications, file names involved, and access control or flow control rules invoked.